Tk_Window _t_k_w_i_n (in) Token for window. Used to map atom or
name relative to a particular display.
char *_n_a_m_e (in) String name for which atom is desired.
Atom _a_t_o_m (in) Atom for which corresponding string name
is desired.
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
These procedures are similar to the Xlib procedures XXXXIIIInnnntttteeeerrrrnnnnAAAAttttoooommmm and
XXXXGGGGeeeettttAAAAttttoooommmmNNNNaaaammmmeeee. TTTTkkkk____IIIInnnntttteeeerrrrnnnnAAAAttttoooommmm returns the atom identifier associated with
string given by _n_a_m_e; the atom identifier is only valid for the display
associated with _t_k_w_i_n. TTTTkkkk____GGGGeeeettttAAAAttttoooommmmNNNNaaaammmmeeee returns the string associated with
_a_t_o_m on _t_k_w_i_n's display. The string returned by TTTTkkkk____GGGGeeeettttAAAAttttoooommmmNNNNaaaammmmeeee is in
Tk's storage: the caller need not free this space when finished with the
string, and the caller should not modify the contents of the returned
string. If there is no atom _a_t_o_m on _t_k_w_i_n's display, then TTTTkkkk____GGGGeeeettttAAAAttttoooommmmNNNNaaaammmmeeee
returns the string ``?bad atom?''.
Tk caches the information returned by TTTTkkkk____IIIInnnntttteeeerrrrnnnnAAAAttttoooommmm and TTTTkkkk____GGGGeeeettttAAAAttttoooommmmNNNNaaaammmmeeee so
that future calls for the same information can be serviced from the cache
without contacting the server. Thus TTTTkkkk____IIIInnnntttteeeerrrrnnnnAAAAttttoooommmm and TTTTkkkk____GGGGeeeettttAAAAttttoooommmmNNNNaaaammmmeeee are
generally much faster than their Xlib counterparts, and they should be